Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-29249 | GEN002760-10 | SV-64275r1_rule | ECAR-1 ECAR-2 ECAR-3 | Medium |
Description |
---|
If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise. |
STIG | Date |
---|---|
Oracle Linux 5 Security Technical Implementation Guide | 2015-03-26 |
Check Text ( C-52717r3_chk ) |
---|
Check the auditing configuration of the system. Procedure: # cat /etc/audit/audit.rules | grep -e "-a exit,always" | grep -i "sched_setscheduler" If the result does not contain "-S sched_setscheduler", this is a finding. |
Fix Text (F-54873r4_fix) |
---|
The "-F arch= Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the /etc/audit/audit.rules file, and add one or more the lines (subject to the dual-architecture discussion above) to enable auditing of operations that change operating system scheduling algorithms and parameters: -a exit,always -F arch= Restart the auditd service: # service auditd restart |